Feedback on the test plan

Some test managers have good experiences with going over the plan in a walkthrough session with the most important stakeholders. Any conflicts soon come to the fore, so that the number of feedback cycles can be kept to a minimum.

Strategy - A potential pitfall is that the communication on the adjusted strategy may be too “strong”. If the client opts for a number of lighter tests than advised, a table is created that shows a lot of ○’s. If this table is shown repeatedly in progress reports or meetings, it gives two impressions: 1) the client is reckless, and 2) the test manager does not entirely approve and is distancing himself from the test approach. For that reason, it is advisable to use this table style only at the beginning and end of the test phase.

Consolidating the test plan

• To make creating a test plan easier and prevent approval delays, it may be decided to have the test plan approved in parts
• The degree of formality of the approval depends on the organisation. In some organisations, it is advisable to enforce the approval formally by having the test plan signed by the client and/or other stakeholders. In other organisations, the sending of approval by e-mail or a verbal confirmation will suffice.